Data sharing events

ABSTRACT

Methods and systems for sharing data among multiple services are described herein. Multiple services may access data from a shared data source. The services may subscribe to data sharing events. A data sharing service may iterate through the shared data source and transmit data retrieved from the shared data source in data sharing events. When the data sharing service reaches the end of the shared data source, the data sharing service may begin iterating through the shared data source again from the beginning. The data sharing events may be transmitted at a predetermined frequency. The services may subscribe to or unsubscribe from the data sharing events.

FIELD

Aspects described herein generally relate to computers, networking,hardware, and software. More specifically, one or more aspects of thedisclosure relate to providing software services with shared data.

BACKGROUND

Multiple software services may each access a shared data source, such asone or more databases. Each of the software services may request toaccess all or a portion of the data stored in the shared data source.The software services may each query the shared data source for data,which may strain or overload the shared data source.

When a new software service is activated, the new software service mayrequest to access all of the data in the shared data source. The newsoftware service may maintain a local data source which comprises a copyof all or a portion of the data stored in the shared data source. Uponactivation, the new software service may request to migrate all datafrom the shared data source to the local data source. This initialmigration of data may overload the shared data source, particularly ininstances where multiple software services are simultaneously performingthis initial migration. It may be preferable to provide data from theshared data source to the multiple software services in a manner thatdoes not overload the shared data source.

The multiple software services may update their respective local datasources in response to changes to the shared data source over time. Theshared data source may provide information to the software servicesabout updates to the shared data source, such as by providing changeevents to the multiple software services when the shared data source ismodified. These updates or change events may be missed by a softwareservice, such as due to a momentary outage or other failure. It may bepreferable to notify the multiple software services of any changes orupdates to the shared data source, or to allow the software services toverify their local data using the shared data source, in a manner thatdoes not overload the shared data source.

SUMMARY

The following presents a simplified summary of various aspects describedherein. This summary is not an extensive overview, and is not intendedto identify required or critical elements or to delineate the scope ofthe claims. The following summary merely presents some concepts in asimplified form as an introductory prelude to the more detaileddescription provided below.

To overcome limitations in the prior art described above, and toovercome other limitations that will be apparent upon reading andunderstanding the present specification, aspects described herein aredirected towards systems, methods, and techniques for managing a shareddata source and providing data sharing events.

In particular, one or more aspects of the disclosure provide ways ofiteratively traversing a shared data source and creating data sharingevents. The data sharing events may be transmitted to services that aresubscribed to the data sharing events. The services may access data inthe data sharing events and store the data in local data sources and/orperform other actions using the data in the data sharing events.

In some embodiments, a plurality of services subscribed to data sharingevents may be determined. A data polling rate corresponding to a datasource may be determined. A data transmission rate corresponding to thedata sharing events may be determined. Data from the data source may beretrieved by iterating through the data source at the data polling rate.The data sharing events may be transmitted to each service of theplurality of services. The data sharing events may be transmitted basedon the data transmission rate. The data sharing events may comprise theretrieved data from the data source.

The data sharing events may each comprise one row of data from the datasource. The data sharing events may comprise one or more useridentifiers. The data polling rate may indicate a maximum number ofrequests over a period of time. The data transmission rate may indicatea maximum number of data sharing events to be transmitted over a periodof time. When an end of the data source has been reached, the iteratingmay be restarted at a beginning of the data source. Determining theplurality of services may comprise receiving a list of addressescorresponding to the plurality of services. The data polling rate andthe data transmission rate may be adjusted based on a size of the datasource. A request may be received, from a service, to subscribe to thedata sharing events. The data source may comprise a shared data sourceaccessed by each service of the plurality of services. The data sourcemay be queried for the data.

In some embodiments, a request may be sent to subscribe to data sharingevents. The request may correspond to a service. In response to therequest, a plurality of data sharing events may be received. Anindication of a user may be retrieved from a data sharing event of theplurality of data sharing events. The indication of the user may bestored in a local data source. The local data source may correspond tothe service. Data corresponding to the user may be retrieved from asource external to the service. The data may be stored in the local datasource.

The indication of the user may comprise a username. The local datasource may be a database maintained by the service. The service may sendthe request using an application programming interface (API). Each datasharing event, of the plurality of data sharing events, may be receivedat a predetermined interval. An external database may be queried for thedata corresponding to the user.

These and additional aspects will be appreciated with the benefit of thedisclosures discussed in further detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of aspects described herein and theadvantages thereof may be acquired by referring to the followingdescription in consideration of the accompanying drawings, in which likereference numbers indicate like features, and wherein:

FIG. 1 depicts an illustrative computer system architecture that may beused in accordance with one or more illustrative aspects describedherein.

FIG. 2 depicts an illustrative cloud-based system architecture that maybe used in accordance with one or more illustrative aspects describedherein.

FIG. 3 is a diagram of a data sharing system according to one or moreillustrative aspects of the disclosure.

FIG. 4 is a flow diagram of a method for sharing data according to oneor more illustrative aspects of the disclosure.

FIG. 5 is a flow diagram of a method for adding a service to a datasharing system according to one or more illustrative aspects of thedisclosure.

FIG. 6 is a flow diagram of a method for receiving data sharing eventsaccording to one or more illustrative aspects of the disclosure.

DETAILED DESCRIPTION

In the following description of the various embodiments, reference ismade to the accompanying drawings identified above and which form a parthereof, and in which is shown by way of illustration various embodimentsin which aspects described herein may be practiced. It is to beunderstood that other embodiments may be utilized and structural andfunctional modifications may be made without departing from the scopedescribed herein. Various aspects are capable of other embodiments andof being practiced or being carried out in various different ways.

As a general introduction to the subject matter described in more detailbelow, aspects described herein are directed towards providing shareddata to multiple services. Multiple services may use data stored in ashared data source, such as a database. For example, the shared datasource may comprise a listing of users authorized to access theservices. A data sharing worker service may iterate through the shareddata source, transmitting data sharing events to all of the services ata predetermined interval. The data sharing events may comprise a portionof the shared data source, such as a row of data. The data sharingservice may iterate continuously through the shared data source, suchthat once the data sharing service reaches the end of the shared datasource, the data sharing service may restart at the beginning of theshared data source. If a new service is implemented, the new service mayrequest to subscribe to the data sharing events from the data sharingservice. The new service may then begin receiving data sharing events.

It is to be understood that the phraseology and terminology used hereinare for the purpose of description and should not be regarded aslimiting. Rather, the phrases and terms used herein are to be giventheir broadest interpretation and meaning. The use of “including” and“comprising” and variations thereof is meant to encompass the itemslisted thereafter and equivalents thereof as well as additional itemsand equivalents thereof. The use of the terms “mounted,” “connected,”“coupled,” “positioned,” “engaged” and similar terms, is meant toinclude both direct and indirect mounting, connecting, coupling,positioning and engaging.

Computing Architecture

Computer software, hardware, and networks may be utilized in a varietyof different system environments, including standalone, networked,remote-access (also known as remote desktop), virtualized, and/orcloud-based environments, among others. FIG. 1 illustrates one exampleof a system architecture and data processing device that may be used toimplement one or more illustrative aspects described herein in astandalone and/or networked environment. Various network nodes 103, 105,107, and 109 may be interconnected via a wide area network (WAN) 101,such as the Internet. Other networks may also or alternatively be used,including private intranets, corporate networks, local area networks(LAN), metropolitan area networks (MAN), wireless networks, personalnetworks (PAN), and the like. Network 101 is for illustration purposesand may be replaced with fewer or additional computer networks. A localarea network 133 may have one or more of any known LAN topology and mayuse one or more of a variety of different protocols, such as Ethernet.Devices 103, 105, 107, and 109 and other devices (not shown) may beconnected to one or more of the networks via twisted pair wires, coaxialcable, fiber optics, radio waves, or other communication media.

The term “network” as used herein and depicted in the drawings refersnot only to systems in which remote storage devices are coupled togethervia one or more communication paths, but also to stand-alone devicesthat may be coupled, from time to time, to such systems that havestorage capability. Consequently, the term “network” includes not only a“physical network” but also a “content network,” which is comprised ofthe data—attributable to a single entity—which resides across allphysical networks.

The components may include data server 103, web server 105, and clientcomputers 107, 109. Data server 103 may provide overall access, controland administration of databases and control software for performing oneor more illustrative aspects describe herein. Data server 103 may beconnected to web server 105 through which users interact with and obtaindata as requested. Alternatively, data server 103 may act as a webserver itself and be directly connected to the Internet. Data server 103may be connected to web server 105 through the local area network 133,the wide area network 101 (e.g., the Internet), via direct or indirectconnection, or via some other network. Users may interact with the dataserver 103 using remote computers 107, 109, e.g., using a web browser toconnect to the data server 103 via one or more externally exposed websites hosted by web server 105. Client computers 107, 109 may be used inconcert with data server 103 to access data stored therein, or may beused for other purposes. For example, from client device 107 a user mayaccess web server 105 using an Internet browser, as is known in the art,or by executing a software application that communicates with web server105 and/or data server 103 over a computer network (such as theInternet).

Servers and applications may be combined on the same physical machines,and retain separate virtual or logical addresses, or may reside onseparate physical machines. FIG. 1 illustrates just one example of anetwork architecture that may be used, and those of skill in the artwill appreciate that the specific network architecture and dataprocessing devices used may vary, and are secondary to the functionalitythat they provide, as further described herein. For example, servicesprovided by web server 105 and data server 103 may be combined on asingle server.

Each component 103, 105, 107, 109 may be any type of known computer,server, or data processing device. Data server 103, e.g., may include aprocessor 111 controlling overall operation of the data server 103. Dataserver 103 may further include random access memory (RAM) 113, read onlymemory (ROM) 115, network interface 117, input/output interfaces 119(e.g., keyboard, mouse, display, printer, etc.), and memory 121.Input/output (I/O) 119 may include a variety of interface units anddrives for reading, writing, displaying, and/or printing data or files.Memory 121 may further store operating system software 123 forcontrolling overall operation of the data processing device 103, controllogic 125 for instructing data server 103 to perform aspects describedherein, and other application software 127 providing secondary, support,and/or other functionality which may or might not be used in conjunctionwith aspects described herein. The control logic 125 may also bereferred to herein as the data server software. Functionality of thedata server software may refer to operations or decisions madeautomatically based on rules coded into the control logic, made manuallyby a user providing input into the system, and/or a combination ofautomatic processing based on user input (e.g., queries, data updates,etc.).

Memory 121 may also store data used in performance of one or moreaspects described herein, including a first database 131 and a seconddatabase 129. In some embodiments, the first database 131 may includethe second database 129 (e.g., as a separate table, report, etc.). Thatis, the information can be stored in a single database, or separatedinto different logical, virtual, or physical databases, depending onsystem design. Devices 105, 107, and 109 may have similar or differentarchitecture as described with respect to device 103. Those of skill inthe art will appreciate that the functionality of data processing device103 (or device 105, 107, or 109) as described herein may be spreadacross multiple data processing devices, for example, to distributeprocessing load across multiple computers, to segregate transactionsbased on geographic location, user access level, quality of service(QoS), etc.

One or more aspects may be embodied in computer-usable or readable dataand/or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices as describedherein. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other device. The modules may be written in a source codeprogramming language that is subsequently compiled for execution, or maybe written in a scripting language such as (but not limited to)HyperText Markup Language (HTML) or Extensible Markup Language (XML).The computer executable instructions may be stored on a computerreadable medium such as a nonvolatile storage device. Any suitablecomputer readable storage media may be utilized, including hard disks,CD-ROMs, optical storage devices, magnetic storage devices, and/or anycombination thereof. In addition, various transmission (non-storage)media representing data or events as described herein may be transferredbetween a source and a destination in the form of electromagnetic wavestraveling through signal-conducting media such as metal wires, opticalfibers, and/or wireless transmission media (e.g., air and/or space).Various aspects described herein may be embodied as a method, a dataprocessing system, or a computer program product. Therefore, variousfunctionalities may be embodied in whole or in part in software,firmware, and/or hardware or hardware equivalents such as integratedcircuits, field programmable gate arrays (FPGA), and the like.Particular data structures may be used to more effectively implement oneor more aspects described herein, and such data structures arecontemplated within the scope of computer executable instructions andcomputer-usable data described herein.

With further reference to FIG. 2, some aspects described herein may beimplemented in a cloud-based environment. FIG. 2 illustrates an exampleof a cloud computing environment (or cloud system) 200. As seen in FIG.2, client computers 211-14 may communicate with a cloud managementserver 210 to access the computing resources (e.g., host servers 203a-203 b (generally referred herein as “host servers 203”), storageresources 204 a-204 b (generally referred herein as “storage resources204”), and network resources 205 a-205 b (generally referred herein as“network resources 205”)) of the cloud system.

Management server 210 may be implemented on one or more physicalservers. The management server 210 may run, for example, CLOUDPLATFORMby Citrix Systems, Inc. of Ft. Lauderdale, Fla., or OPENSTACK, amongothers. Management server 210 may manage various computing resources,including cloud hardware and software resources, for example, hostcomputers 203, data storage devices 204, and networking devices 205. Thecloud hardware and software resources may include private and/or publiccomponents. For example, a cloud may be configured as a private cloud tobe used by one or more particular customers or client computers 211-14and/or over a private network. In other embodiments, public clouds orhybrid public-private clouds may be used by other customers over an openor hybrid networks.

Management server 210 may be configured to provide user interfacesthrough which cloud operators and cloud customers may interact with thecloud system 200. For example, the management server 210 may provide aset of application programming interfaces (APIs) and/or one or morecloud operator console applications (e.g., web-based or standaloneapplications) with user interfaces to allow cloud operators to managethe cloud resources, configure the virtualization layer, manage customeraccounts, and perform other cloud administration tasks. The managementserver 210 also may include a set of APIs and/or one or more customerconsole applications with user interfaces configured to receive cloudcomputing requests from end users via client computers 211-14, forexample, requests to create, modify, or destroy virtual machines withinthe cloud. Client computers 211-14 may connect to management server 210via the Internet or some other communication network, and may requestaccess to one or more of the computing resources managed by managementserver 210. In response to client requests, the management server 210may include a resource manager configured to select and provisionphysical resources in the hardware layer of the cloud system based onthe client requests. For example, the management server 210 andadditional components of the cloud system may be configured toprovision, create, and manage virtual machines and their operatingenvironments (e.g., hypervisors, storage resources, services offered bythe network elements, etc.) for customers at client computers 211-14,over a network (e.g., the Internet), providing customers withcomputational resources, data storage services, networking capabilities,and computer platform and application support. Cloud systems also may beconfigured to provide various specific services, including securitysystems, development environments, user interfaces, and the like.

Certain clients 211-14 may be related, for example, different clientcomputers creating virtual machines on behalf of the same end user, ordifferent users affiliated with the same company or organization. Inother examples, certain clients 211-14 may be unrelated, such as usersaffiliated with different companies or organizations. For unrelatedclients, information on the virtual machines or storage of any one usermay be hidden from other users.

Referring now to the physical hardware layer of a cloud computingenvironment, availability zones 201-02 (or zones) may refer to acollocated set of physical computing resources. Zones may begeographically separated from other zones in the overall cloud ofcomputing resources. For example, zone 201 may be a first clouddatacenter located in California, and zone 202 may be a second clouddatacenter located in Florida. Management server 210 may be located atone of the availability zones, or at a separate location. Each zone mayinclude an internal network that interfaces with devices that areoutside of the zone, such as the management server 210, through agateway. End users of the cloud (e.g., clients 211-14) might or mightnot be aware of the distinctions between zones. For example, an end usermay request the creation of a virtual machine having a specified amountof memory, processing power, and network capabilities. The managementserver 210 may respond to the user's request and may allocate theresources to create the virtual machine without the user knowing whetherthe virtual machine was created using resources from zone 201 or zone202. In other examples, the cloud system may allow end users to requestthat virtual machines (or other cloud resources) are allocated in aspecific zone or on specific resources 203-05 within a zone.

In this example, each zone 201-02 may comprise an arrangement of variousphysical hardware components (or computing resources) 203-05, forexample, physical hosting resources (or processing resources), physicalnetwork resources, physical storage resources, switches, and additionalhardware resources that may be used to provide cloud computing servicesto customers. The physical hosting resources in a cloud zone 201-02 maycomprise one or more computer servers 203, such as the virtualizationservers 301 described above, which may be configured to create and hostvirtual machine instances. The physical network resources in a cloudzone 201 or 202 may include one or more network elements 205 (e.g.,network service providers) comprising hardware and/or softwareconfigured to provide a network service to cloud customers, such asfirewalls, network address translators, load balancers, virtual privatenetwork (VPN) gateways, Dynamic Host Configuration Protocol (DHCP)routers, and the like. The storage resources in the cloud zone 201-02may comprise storage disks (e.g., solid state drives (SSDs), magnetichard disks, etc.) and other storage devices.

The example cloud computing environment shown in FIG. 2 also may includea virtualization layer with additional hardware and/or softwareresources configured to create and manage virtual machines and provideother services to customers using the physical resources in the cloud.The virtualization layer may include hypervisors, along with othercomponents to provide network virtualizations, storage virtualizations,etc. The virtualization layer may be as a separate layer from thephysical resource layer, or may share some or all of the same hardwareand/or software resources with the physical resource layer. For example,the virtualization layer may include a hypervisor installed in each ofthe virtualization servers 203 with the physical computing resources.Known cloud systems may alternatively be used, e.g., WINDOWS AZURE(Microsoft Corporation of Redmond Wash.), AMAZON EC2 (Amazon.com Inc. ofSeattle, Wash.), IBM BLUE CLOUD (IBM Corporation of Armonk, N.Y.), orothers.

Iterative Data Sharing

FIG. 3 is a diagram of a data sharing system according to one or moreillustrative aspects of the disclosure. Shared data source 320 maycomprise data used by one or more services. Services 340-42 may bepermitted to read from and/or write to the data source 320. The shareddata source 320 may comprise one or more databases, or any other datastorage system. For example, the shared data source 320 may compriseuser identification for users subscribed to one or more of the services340-42. The shared data source 320 may comprise both data that is and isnot transmitted via data sharing events. For example, if the shared datasource 320 is a database, the database may comprise one or more columnsthat are not transmitted in the data sharing events. In another example,the shared data source 320 may comprise multiple types of data, and asingle type of data may be transmitted in data sharing events.

The services 340-42 may retrieve data from the shared data source 320via data sharing events and/or directly. The services 340-42 may querythe shared data source 320 for data. The services 340-42 may cause theshared data source 320 to store data, or modify data stored by theshared data source 320.

Data sharing worker service 310 may retrieve data from the shared datasource 320 and periodically transmit data sharing events. The datasharing worker service 310 may comprise a stateless service. The datasharing worker service 310 may comprise one or more instances. The datasharing worker service 310 may query the shared data source 320 fordata, and transmit the data as a data sharing event. The data sharingworker service 310 may poll the shared data source 320 at a data pollingrate configured to prevent the shared data source 320 from becomingoverloaded. The data polling rate may be adjusted based on measuredperformance values for the shared data source 320. For example, if theshared data source 320 is above a threshold amount of processor usage,the data polling rate may be reduced.

Each data sharing event may comprise data received from the shared datasource 320. For example, if the shared data source 320 is a database,each data sharing event may comprise one row of data from the database,or one cell from the database. In another example, if the shared datasource 320 stores user identification numbers, each data sharing eventmay comprise one user identification number. Data sharing events may betransmitted by the data sharing worker service 310 to an event pipeline330. Although shown separately in FIG. 3, the data sharing workerservice 310 may comprise the event pipeline 330.

The event pipeline 330 may transmit a data sharing event to all servicessubscribed to the data sharing system. In FIG. 3, the event pipeline 330is illustrated as transmitting data sharing events to services 340-42.Each time the event pipeline 330 receives a data sharing event, thatdata sharing event may be transmitted to all of the services 340-42. Anynumber of services may receive data from the event pipeline 330.Services may be added to or removed from the list of services that eventpipeline 330 transmits data sharing events to. A service may be added orremoved from the event pipeline 330 at any time.

Although data sharing events are described as being transmitted toservice 340-42, in some embodiments the services 340-42 may retrieve thedata sharing events. For example, the services 340-42 may retrieve thedata sharing events from a predetermined address.

Services 340-42 may comprise services that access data stored in theshared data source 320. The services 340-32 may each maintain their ownrespective local data 350-52. For example, local data 351 may comprise adatabase maintained by service 341. The local data 350-52 may comprise acopy of all or a portion of the data stored in the shared data source320. Upon receiving a data sharing event via the event pipeline 330, theservices 340-42 may update their respective local data 350-52 and/orperform other actions based on the data sharing event. For example, ifthe shared data source 320 comprises a catalog of domain names, uponreceiving a data sharing event comprising a domain name, the service 342may store the domain name in its local data 352 and access a servercorresponding to the domain name to retrieve a web page. In anotherexample, if the data sharing event comprises information describing aproduct, the service 340 may store the received information in the localdata 350, and may access an external database to retrieve a photographcorresponding to the product.

FIG. 4 is a flow diagram of a method 400 for sharing data according toone or more illustrative aspects of the disclosure. In one or moreembodiments, one or more steps illustrated in FIG. 4 may be performed byone or more computing devices or entities. For example, portions of thesteps illustrated in FIG. 4 may be performed by one or more computingdevices, such as data server 103, web server 105, client computer 107,client computer 109, or by one or more elements of the cloud computingenvironment 200. The steps illustrated in FIG. 4 may be embodied incomputer-executable instructions that are stored in a computer-readablemedium, such as a non-transitory computer readable medium. The stepsillustrated in FIG. 4 need not all be performed in the order specified,and some steps may be omitted or changed in order.

At step 410, a connection may be established with one or more services.The services may request to receive data sharing events. To request toreceive the data sharing events, the services may provide addresses fortransmitting the data sharing events. A database or list of subscribersto the data sharing events may be maintained. For example, services340-42 may transmit messages to the data sharing worker service 310requesting that the data sharing events be transmitted to services340-42.

Although illustrated as the initial step in method 400, services maysubscribe to or unsubscribe from the data sharing events at any time. Ifa data sharing event or a predetermined threshold number of data sharingevents are transmitted to a service, but the transmission fails, thatservice may be removed from receiving further data sharing events. Forexample, if service 341 was subscribed to receive data sharing events,but a connection could no longer be established with service 341, thenthe service 341 may be removed from receiving further data sharingevents. In this example, the data sharing worker service 310 mayperiodically attempt to reestablish the connection with the service 341,and if the connection is reestablished, then the data sharing workerservice 310 may resume providing the service 341 with data sharingevents.

At step 415, a data polling rate may be received or determined. The datapolling rate may indicate a rate at which data can be retrieved from theshared data source. The data polling rate may indicate a maximum numberof queries over a specified period of time, a maximum volume of data toretrieve in a specified amount of time, a maximum number of rows of datato retrieve in a specified amount of time, or any other rate foraccessing data. The data polling rate may be preconfigured or preset.

The data polling rate may be determined based on a current performanceof the shared data source. The data polling rate may be determined basedon an amount of available memory, an indicator of CPU performance, anindicator of network usage, or any other data corresponding to theshared data source. The data polling rate may be adjusted based on theperformance of the shared data source. The data polling rate may beadjusted at a set interval, such as every five minutes, or after apredetermined number of queries.

The data polling rate may be determined based on an amount of data inthe shared data source and/or a desired cycle length. For example, thedata polling rate may be determined so that all data in the shared datasource is traversed once per day.

At step 420, a data transmission rate may be received or determined. Thedata transmission rate may indicate a rate at which data sharing eventsare to be transmitted to subscribed services. The transmission rate mayindicate a maximum rate, minimum rate, targeted average rate, a range ofacceptable rates, or any other measure for transmitting data. The datatransmission rate may be altered at any time during the method 400. Thedata transmission rate may be adjusted based on a performancemeasurement, such as a performance measurement of the shared datasource. The data transmission rate may indicate a maximum amount of datato be transmitted in a predetermined time period. For example, the datatransmission rate may indicate that a maximum of five rows of data maybe transmitted each second. The data transmission rate may indicate adelay between data sharing events. For example, the data transmissionrate may indicate that a delay of two seconds should occur between eachdata sharing event. The data transmission rate may indicate an amount ofdata to be transmitted in each data sharing event. For example, the datatransmission rate may indicate that ten rows of data should betransmitted in each data sharing event, or that a maximum of onemegabyte of data should be transmitted in each data sharing event. Thedata transmission rate may be determined based on an amount of data inthe shared data source and/or a desired cycle length.

At step 430, a data sharing event may be transmitted, where the datasharing event comprises a first segment of data retrieved from theshared data source. The first segment of data may comprise a first rowof a database or a table. The method 400 may iteratively traverse theshared data source, and may use any method for iterating through theshared data source. For example, the first segment of data may comprisethe oldest data or the newest data in the shared data source. The shareddata source may be iterated through in a random fashion, or using anyother appropriate algorithm for iterating through a set of data. Forexample, if the shared data comprises a plurality of book titles, thebook titles may be sorted in alphabetical order and traversed in thatorder.

At step 440, the method 400 may wait for the next transmission time. Forexample, if the data transmission rate indicates that two seconds shouldpass between data sharing events, then the method 400 may wait twoseconds at step 440. If the data transmission rate indicates a maximumamount of data to be transmitted over a period of time, the method 400may determine, at step 440, whether to continue or delay in order tosatisfy the transmission rate. After waiting for the amount of timedictated by the data transmission rate, the method 400 may proceed tostep 450. The method 400 may also wait at step 440 based on the datapolling rate.

At step 450 the next segment of data from the shared data source may betransmitted in a data sharing event. For example, if the datatransmission rate received at step 420 indicates that 25 rows of datashould be transmitted in each data sharing event, then the next 25 rowsof data may be transmitted at step 450.

At step 460, the shared data source may be examined to determine whetherall data has been sent. If the shared data source is a database that isbeing transmitted in order from the first to last row, step 460 maydetermine whether the last row has been reached. If the last row hasbeen reached, the method may wait for the next transmission time at step470, and then transmit the first segment of data at step 430. The method400 may continuously transmit data from the shared data source 320,repeating at the beginning of the shared data source 320 after all datahas been transmitted via data sharing events. Regardless of when a newservice subscribes to the data sharing events, the new service mayreceive all data in the shared data source 320 via data sharing events.The data transmission rate may control how quickly the new service willreceive the entire set of data in the shared data source 320.

If, at step 460, all data has not yet been sent, the method may proceedto step 440 to wait for the next transmission time, and then send thenext segment of data in a data sharing event at step 450. The method 400may continue iterating through the shared data source indefinitely inthis manner, returning to the beginning of the shared data source eachtime a cycle is complete.

FIG. 5 is a flow diagram of a method 500 for adding a service to a datasharing system according to one or more illustrative aspects of thedisclosure. In one or more embodiments, one or more steps illustrated inFIG. 5 may be performed by one or more computing devices or entities.For example, portions of the steps illustrated in FIG. 5 may beperformed by one or more computing devices, such as data server 103, webserver 105, client computer 107, client computer 109, or by one or moreelements of the cloud computing environment 200. The steps illustratedin FIG. 5 may be embodied in computer-executable instructions that arestored in a computer-readable medium, such as a non-transitory computerreadable medium. The steps illustrated in FIG. 5 need not all beperformed in the order specified, and some steps may be omitted orchanged in order.

At step 510 a new service may be activated. The new service may comprisean update to a previously operating service. The new service may be acloud service. The new service may comprise any type of softwareservice, such as an email client or a file sharing service. Althoughdescribed as a new service, the service may be any service that was notpreviously subscribed to data sharing events.

At step 520, the new service may request to subscribe to data sharingevents. The new service may transmit an address corresponding to the newservice. The new service may use an API to request to subscribe to thedata sharing events. An administrator of the data sharing service maymanually add the new service to the list of subscribed services. Theadministrator of the data sharing service may authorize the new serviceto receive data sharing events.

At step 530 the new service may be subscribed to the data sharingevents. For example, an address corresponding to the new service may beadded to a list or database used to maintain addresses to transmit datasharing events to.

At step 540 data sharing events may be transmitted to all subscribedservices, including the new service. Each data sharing event may betransmitted simultaneously, or approximately simultaneously, to each ofthe subscribed services.

At step 550 the new service may receive a data sharing event and respondto the data sharing event. Each service may be configured to operatedifferently upon receiving a data sharing event. The service may usedata in the data sharing event to update its local data, to retrieveother data from an external database, to perform calculations, and/orfor other purposes.

FIG. 6 is a flow diagram of a method 600 for receiving data sharingevents according to one or more illustrative aspects of the disclosure.In one or more embodiments, one or more steps illustrated in FIG. 6 maybe performed by one or more computing devices or entities. For example,portions of the steps illustrated in FIG. 6 may be performed by one ormore computing devices, such as data server 103, web server 105, clientcomputer 107, client computer 109, or by one or more elements of thecloud computing environment 200. The steps illustrated in FIG. 6 may beembodied in computer-executable instructions that are stored in acomputer-readable medium, such as a non-transitory computer readablemedium. The steps illustrated in FIG. 6 need not all be performed in theorder specified, and some steps may be omitted or changed in order.

At step 610, a service may receive a data sharing event. As describedabove, the data sharing event may comprise a portion of data from ashared data source. For example, the data sharing event may comprise oneor more usernames. The data sharing event may comprise one or more rowsof data in a database. For example, the data sharing event may comprisea row of user data having a username, an email address, and anindication of services that the user is subscribed to. In anotherexample, the data sharing event may comprise a row of data on a product,which may comprise a product name, a stock keeping unit (SKU), and aprice.

At step 620, the service may determine whether the received data waspreviously received by the service. The service may determine whetherthe received data, or an indication of the received data, is stored inthe local data corresponding to the service. For example, if thereceived data comprises a user ID, the service may determine whetheruser data corresponding to the user ID is stored in the local data. Theservice may determine, at step 620, whether the received data comprisesan update or modification to data stored in the local data.

If the data was not found in the local data, or if the data comprises anupdate or modification to the local data, the method 600 may proceed tostep 630. Otherwise, the method 600 may end at step 640. At step 630,the service may add the received data to the local data, update thelocal data based on the received data, and/or perform other operationsusing the received data at step 640. The service may access the shareddata source to retrieve additional data corresponding to the datasharing event. For example, if the data sharing event comprises a userID, the service may access the shared data source to retrieve an emailaddress or other data corresponding to the user ID. The method 600 maythen end at step 650, until another data sharing event is received. Theservice may continue receiving data sharing events and updating itslocal data, as the data sharing worker service iterates through thelocal data source.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are described asexample implementations of the following claims.

What is claimed is:
 1. A method comprising: determining a plurality ofservices subscribed to data sharing events; determining a data pollingrate corresponding to a data source; determining a data transmissionrate corresponding to the data sharing events; retrieving, by iteratingthrough the data source at the data polling rate, data from the datasource; and transmitting, based on the data transmission rate and toeach service of the plurality of services, the data sharing eventscomprising the data from the data source.
 2. The method of claim 1,wherein each of the data sharing events comprises one row of data fromthe data source.
 3. The method of claim 1, wherein each of the datasharing events comprises one or more user identifiers.
 4. The method ofclaim 1, wherein the data polling rate indicates a maximum number ofrequests over a period of time.
 5. The method of claim 1, wherein thedata transmission rate indicates a maximum number of data sharing eventsto be transmitted over a period of time.
 6. The method of claim 1,wherein iterating through the data source comprises, when an end of thedata source has been reached, restarting the iterating at a beginning ofthe data source.
 7. The method of claim 1, wherein determining theplurality of services comprises receiving a list of addressescorresponding to the plurality of services.
 8. An apparatus comprising:one or more processors, and memory storing instructions that, whenexecuted by the one or more processors, cause the apparatus to:determine a plurality of services subscribed to data sharing events;determine a data polling rate corresponding to a data source; determinea data transmission rate corresponding to the data sharing events;retrieving, by iterating through the data source at the data pollingrate, data from the data source; and transmit, based on the datatransmission rate and to each service of the plurality of services, thedata sharing events comprising the data from the data source.
 9. Theapparatus of claim 8, wherein the instructions, when executed by the oneor more processors, cause the apparatus to adjust, based on a size ofthe data source, the data polling rate and the data transmission rate.10. The apparatus of claim 8, wherein the instructions, when executed bythe one or more processors, cause the apparatus to, upon reaching an endof the data source, resume iterating through the data source from abeginning of the data source.
 11. The apparatus of claim 8, wherein theinstructions, when executed by the one or more processors, cause theapparatus to receive, from a service, a request to subscribe to the datasharing events.
 12. The apparatus of claim 8, wherein each of the datasharing events comprises one or more rows of data from the data source.13. The apparatus of claim 8, wherein the data source comprises a shareddata source accessed by each service of the plurality of services. 14.The apparatus of claim 8, wherein the instructions, when executed by theone or more processors, cause the apparatus to query the data source forthe data.
 15. One or more non-transitory computer readable media storingcomputer executable instructions that, when executed by a dataprocessing system, configure the system to perform: determining aplurality of services subscribed to data sharing events; determining adata polling rate corresponding to a data source; determining a datatransmission rate corresponding to the data sharing events; retrieving,by iterating through the data source at the data polling rate, data fromthe data source; and transmitting, based on the data transmission rateand to each service of the plurality of services, the data sharingevents comprising the data from the data source.
 16. The computerreadable media of claim 15, wherein each of the data sharing eventscomprises one row of data from the data source.
 17. The computerreadable media of claim 15, wherein each of the data sharing eventscomprises one or more user identifiers.
 18. The computer readable mediaof claim 15, wherein the data polling rate indicates a maximum number ofrequests over a period of time.
 19. The computer readable media of claim15, wherein the data transmission rate indicates a maximum number ofdata sharing events to be transmitted over a period of time.
 20. Thecomputer readable media of claim 15, wherein iterating through the datasource comprises, when an end of the data source has been reached,restarting the iterating at a beginning of the data source.
 21. Thecomputer readable media of claim 15, wherein determining the pluralityof services comprises receiving a list of addresses corresponding to theplurality of services.